Dynamic Feature Scoring uses scoring rules to dynamically evaluate elements at run time. During OpenCities Map file open and load events, all non-XFM feature elementsare evaluated against the set of DFS rules. The DFS engine maintains a feature rules list read from XML files specified in the configuration variable MS_GEOXFM_DYNAMICFEATURESCORING_FILES.

Following is a procedure that can be used to create a custom DFS rule file and make it available to the OpenCities Map project. For example, by default, OpenCities Map recognizes cell features as individual features based on their cell name. But if the same feature has different cell names then OpenCities Map would infer two different features. Custom DFS rules can be used to adjust this behavior. Two examples are below.

Any element that has an entity number of 100 will be inferred as a LIGHTPOLE feature. This assumes standard MicroStation attribute linkages are used to link the features to a database table, identified as entity 100 in the MSCATALOG table.

<FeatureScoringRules minScore="100">
      <Feature useCriteria="" name="LIGHTPOLE">
            <Rule type="DBEntity" score="100" entity="100"/>
      </Feature>
</FeatureScoringRules>

Any cell (elementType=2) with the listed cellName will be inferred as a LIGHPOLE2 feature.

<FeatureScoringRules minScore="100">
      <Feature useCriteria="" name="LIGHTPOLE2">
            <Rule type="Element" score="100" cellName="LIGHTPOLE_DOUBLE_OUTREACH" elementType="2"/>
            <Rule type="Element" score="100" cellName="LIGHTPOLE_V_OUTREACH" elementType="2"/>
            <Rule type="Element" score="100" cellName="LIGHTPOLE_SINGLE_OUTREACH" elementType="2"/>
            <Rule type="Element" score="100" cellName="LIGHTPOLE_SINGLE_OUTREACH_SMALL" elementType="2"/>
            <Rule type="Element" score="100" cellName="LIGHTPOLE_DOUBLE_OUTREACH_SMALL" elementType="2"/>
            <Rule type="Element" score="100" cellName="LIGHTPOLE" elementType="2"/>
      </Feature>
</FeatureScoringRules>